OCPBUGS-96622: Bump golang.org/x/net to v0.55.0 - #722

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@sunku5494: This pull request references Jira Issue OCPBUGS-96622, which is invalid:

• expected Jira Issue OCPBUGS-96622 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

_{Comment @coderabbitai help to get the list of available commands.}

/lgtm
/approve
/label backport-risk-assessed

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-upgrade
/test e2e-azure-csi
/test e2e-azure-file-csi
/test e2e-gcp-csi
/test e2e-vsphere-csi

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RomanBednar, sunku5494

The full list of commands accepted by this bot can be found here.

The pull request process is described here

/label jira/skip-dependency-bug-check
as its fixed in main already

@prabhapa: The label(s) /label jira/skip-dependency-bug-check cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, rebase/manual, cluster-config-api-changed, run-integration-tests, verified, ready-for-human-review, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/skip-dependent-bug-check, jira/valid-bug, ok-to-test, stability-fix-approved, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

/label jira/skip-dependent-bug-check
as its fixed in main already

@sunku5494: This pull request references Jira Issue OCPBUGS-96622, which is valid. The bug has been moved to the POST state.

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

@sunku5494: all tests passed!

Full PR test history. Your PR dashboard.

/verified by CI

@sunku5494: This PR has been marked as verified by CI.

@sunku5494: Jira Issue Verification Checks: Jira Issue OCPBUGS-96622
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-96622 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓